HURD Live CD |
|
| Company / developer | GNU Project Thomas Bushnell Roland McGrath Marcus Brinkmann Neal Walfield |
| Programmed in | Assembly, C |
| OS family | Unix-like |
| Working state | Current |
| Source model | Free and open source software |
| Latest unstable release | Arch Hurd LiveCD / 17 August 2011 |
| Supported platforms | i386 architecture |
| Kernel type | Microkernel server/client |
| Userland | GNU and others |
| Default user interface | Bash |
| License | GNU General Public License |
| Official website | http://www.gnu.org/software/hurd/ |
GNU Hurd (usually referred to as the Hurd) is a computer operating system kernel designed as a replacement for Unix,[1] released as free software under the GNU General Public License. It has been under development since 1990 by the GNU Project of the Free Software Foundation.
GNU Hurd consists of a set of protocols and server processes (or daemons, in Unix terminology) that run on the GNU Mach microkernel; together they are intended to form the kernel of the GNU operating system.[1] The Hurd aims to surpass Unix operating systems in functionality, security, and stability, while remaining largely compatible with them. The GNU Project chose the microkernel server–client architecture for the operating system, due to perceived advantages over the traditional Unix monolithic kernel architecture.[2]
Contents |
HURD is a mutually recursive acronym, standing for HIRD of Unix-replacing daemons, where HIRD stands for HURD of interfaces representing depth. As both hurd and hird are just alternate spellings for the English word herd, the full name GNU Hurd is also a play on the words herd of gnus, reflecting how the kernel works.[3]
Development on the GNU operating system began in 1984 and initially made good progress. Free GNU tools started to acquire a good reputation and were often adopted in preference to proprietary tools provided by system vendors. By the early 1990s, the only major component missing was the kernel.[4]
Development on the Hurd began in 1990 after an abandoned kernel attempt in 1986, based on the research TRIX operating system developed by Professor Steve Ward and his group at MIT's Laboratory for Computer Science (LCS).[5] According to Thomas Bushnell, the initial Hurd architect, their early plan was to adapt the 4.4BSD-Lite kernel and, in hindsight, "It is now perfectly obvious to me that this would have succeeded splendidly and the world would be a very different place today".[6] However, in 1987, due to a lack of cooperation from the Berkeley programmers, Richard Stallman proposed instead to use the Mach microkernel developed at Carnegie Mellon University. Work on this was delayed for three years due to uncertainty over whether CMU would release the Mach code under a suitable license.[5]
With the release of the Linux kernel in 1991, the primary user of GNU's userland components soon became operating systems based on the Linux kernel (Linux distributions), prompting the coining of the controversial term GNU/Linux.
Development of the Hurd has proceeded slowly. Despite an optimistic announcement by Stallman in 2002[7] predicting a release of GNU/Hurd later that year, the Hurd is still not considered suitable for production environments. Development in general has not met expectations, and there are still bugs and missing features.[8] This has resulted in a poorer product than many (including Stallman) had expected.[9] In 2010, after twenty years under development, Stallman said that he was "not very optimistic about the GNU Hurd. It makes some progress, but to be really superior it would require solving a lot of deep problems", but added that "finishing it is not crucial" for the GNU system because a free kernel already existed in Linux, and completing Hurd would not address the main remaining problem for a free operating system: device support.[10]
The Debian project, among others, have worked on the Hurd project to produce binary distributions of Hurd-based GNU operating systems for IBM PC compatible systems.
Unlike most Unix-like kernels, the Hurd uses a server–client architecture, built on a microkernel that is responsible for providing the most basic kernel services – coordinating access to the hardware: the CPU (through process management and scheduling), RAM (via memory management), and other various input/output devices (via I/O scheduling) for sound, graphics, mass storage, etc. In theory the microkernel design would allow for all device drivers to be built as servers working in user space, but today most drivers of this kind are still contained in the GNU Mach kernel space. This is because, initially, user-space drivers would have suffered from performance loss, due to the overhead of the Mach interprocess communication. With the performance of today's machines, it is possible that this overhead would no longer cause a significant performance problem.[11]
From early on, the Hurd was developed to use GNU Mach as the microkernel. This was a technical decision made by Richard Stallman, who thought it would speed up the work by saving a large part of it. He has admitted that he was wrong about that.[12] Other Unix-like systems working on the Mach microkernel include OSF/1, Lites, and MkLinux. Mac OS X and NeXTSTEP use hybrid kernels based on Mach.
In 2007, Hurd developers Neal Walfield and Marcus Brinkmann gave a critique of the Hurd architecture, known as "the critique",[13] and a proposal for how a future system may be architected, known as "the position paper".[14]
From 2004 onward, various efforts were launched to port the Hurd to more modern microkernels. The L4 microkernel was the original choice in 2004, but progress slowed to a halt. Nevertheless, during 2005, Hurd developer Neal Walfield finished the initial memory management framework for the L4/Hurd port, and Marcus Brinkmann ported essential parts of glibc; namely, getting the process startup code working, allowing programs to run, thus allowing the first user programs (trivial ones such as the hello world program in C) to run.
Since 2005 Brinkmann and Walfield started researching Coyotos as a new kernel for HURD.[15][16] In 2006, Brinkmann met with Jonathan Shapiro (a primary architect of the Coyotos Operating System) to aid in and discuss the use of the Coyotos kernel for GNU/Hurd. In further discussion HURD developers realised that Coyotos (as well as other similar kernels) are not suitable for HURD.
In 2008, Neal Walfield began working on the Viengoos microkernel as a modern native kernel for HURD. As of 2009[update], development on Viengoos is paused due to Walfield lacking time to work on it.[17]
In the meantime, others have continued working on the Mach variant of Hurd.[18]
A number of traditional Unix concepts are replaced or extended in the Hurd.
Under Unix, every running program has an associated user id, which normally corresponds to the user that started the process. This id largely dictates the actions permitted to the program. No outside process can change the user id of a running program. A Hurd process, on the other hand, runs under a set of user ids, which can contain multiple ids, one, or none. A sufficiently privileged process can add and remove ids to another process. For example there is a password server that will hand out ids in return for a correct login password.
Regarding the file system, a suitable program can be designated as a translator for a single file or a whole directory hierarchy. Every access to the translated file, or files below a hierarchy in the second case, is in fact handled by the program. For example a file translator may simply redirect read and write operations to another file, not unlike a Unix symbolic link. The effect of Unix mounting is achieved by setting up a filesystem translator (using the "settrans" command). Translators can also be used to provide services to the user. For example, the ftpfs translator allows a user to encapsulate remote FTP sites within a directory. Then, standard tools such as ls, cp, and rm can be used to manipulate files on the remote system. Even more powerful translators are ones such as UnionFS, which allows a user to unify multiple directories into one; thus listing the unified directory reveals the contents of all the directories (a feature that is missing in many Unixes, although available in modern BSDs).
The Hurd requires a multiboot-compliant boot loader, such as GRUB.
According to the Debian documentation there are 24 servers (18 core servers and 6 file system servers) named as follows:[19]
The servers collectively implement the POSIX API, with each server implementing a part of the interface. For instance, the various filesystem servers each implement the filesystem calls. The storage server will work as a wrapping layer, similar to the block layer of Linux. The equivalent of VFS of Linux is achieved by libdiskfs and libpager libraries.
Hurd-based GNU distributions include:
|
|||||||||||||||||||